Replace <command> markup with <userinput>.

diff --git a/xmldoc/chapters/build.xml b/xmldoc/chapters/build.xml
index c49cdbf0e8f9fe70dbdcb1e8744e8eef2265f9b1..abc68c53cf84b68efec64c0e555b492f41aeb9be 100644 (file)
--- a/xmldoc/chapters/build.xml
+++ b/xmldoc/chapters/build.xml
@@ -20,7 +20,7 @@ Linux, Solaris, and a variety of processors and compilers.
   <para>
   In most cases, the code is as simple to build as running:
 </para>
-<para><command> ./configure &amp;&amp; make</command></para>
+<para><userinput> ./configure &amp;&amp; make</userinput></para>
   <para><ulink url="http://expat.sourceforge.net">Expat</ulink> 
 is strongly recommended for source builds as it is
 required for reading all the XML formats such as GPX.
@@ -31,7 +31,7 @@ is recommended for OS/X and Linux if you want to use a USB Garmin.
 <para>There are additional flags that can be passed to configure to
  customize your build of GPSBabel.   
 </para>
-<para><command>./configure --help</command></para> 
+<para><userinput>./configure --help</userinput></para> 
 <para>
 lists all the supported options, but additionally we have:
  <option>--disable-shapefile</option> Excludes the shapefile support.

diff --git a/xmldoc/chapters/styles.xml b/xmldoc/chapters/styles.xml
index 2a80eb333368d01ee1c0e9b72304690e4ff9f094..e471f74c75a098eccbc9d0cd0d50149aec7c1f8c 100644 (file)
--- a/xmldoc/chapters/styles.xml
+++ b/xmldoc/chapters/styles.xml
@@ -29,7 +29,7 @@ format use that file.  If you created a new style file called
 "mystyle.style" and you want to write the  waypoints from
 a GPX file named "mine.gpx" to it, you would issue a command like:
 </para>
-<para><command>gpsbabel -i gpx -f mine.gpx -o xcsv,style=mystyle.style -f mine.new</command></para>
+<para><userinput>gpsbabel -i gpx -f mine.gpx -o xcsv,style=mystyle.style -f mine.new</userinput></para>
 <para>
 You might then examine <filename>mine.new</filename> to see if it met
 your expectations.  If not, you could continue to tweak 

diff --git a/xmldoc/chapters/use.xml b/xmldoc/chapters/use.xml
index 21b81bc3958c7139549fdc328c3fc88ef67e7727..a5c4816bfb2f4103026ac50878b886da08171623 100644 (file)
--- a/xmldoc/chapters/use.xml
+++ b/xmldoc/chapters/use.xml
@@ -33,7 +33,7 @@ options you need to know to do those things:
 The <parameter class="command">format</parameter> parameters in the above list
 refer to the names of formats or file types supported by GPSBabel. 
 </para>
-<para><command>gpsbabel -? </command></para>
+<para><userinput>gpsbabel -? </userinput></para>
 <para>will always show you the supported file types.  In this document, the
 various supported formats are listed in <xref linkend="The_Formats" />.  The 
 name that you would use on the command line follows the format name in 
@@ -53,15 +53,15 @@ name of a file to be read or written.
          this program, just tell it what you're reading, where to read
          it from, what you're writing, and what to write it to.  For
          example:</para>
-         <para><command>gpsbabel -i geo -f /tmp/geocaching.loc -o gpx -F /tmp/geocaching.gpx</command></para>
+         <para><userinput>gpsbabel -i geo -f /tmp/geocaching.loc -o gpx -F /tmp/geocaching.gpx</userinput></para>
          <para>tells it to read the file "/tmp/geocaching.loc" in geocaching.com
          format and create a new file in GPX format.</para>
          <para> This command will read from a Magellan unit attached
          to the first serial port on a Linux system (device names will
          vary on other OSes) and write them as a geocaching loc file.
          The second command does the same on Microsoft Windows.</para>
-         <para><command>gpsbabel -i magellan -f /dev/ttyS0 -o geo -F mag.loc</command></para>
-         <para><command>gpsbabel -i magellan -f com1 -o geo -F mag.loc</command></para>
+         <para><userinput>gpsbabel -i magellan -f /dev/ttyS0 -o geo -F mag.loc</userinput></para>
+         <para><userinput>gpsbabel -i magellan -f com1 -o geo -F mag.loc</userinput></para>
          <para>Optionally, you may specify <parameter moreinfo="none">"-s"</parameter> in any command line.  This
          causes the program to ignore any "short" names that may be
          present in the source data format and synthesize one from the
@@ -73,8 +73,8 @@ name of a file to be read or written.
          the 'GC1234' ones that are optimized for NMEA-only receivers.
          A geocacher with a Magellan receiver may thus find commands
          like this useful.</para>
-         <para><command>gpsbabel -s -i geo -f geocaching.loc -o magellan -F /dev/ttyS0  </command></para>
-       <para><command>gpsbabel -s -i geo -f geocaching.loc -o magellan -F com1</command></para>
+         <para><userinput>gpsbabel -s -i geo -f geocaching.loc -o magellan -F /dev/ttyS0  </userinput></para>
+       <para><userinput>gpsbabel -s -i geo -f geocaching.loc -o magellan -F com1</userinput></para>
       </sect1>
       <sect1 id="Suboptions">
        <title>Suboptions</title>
@@ -89,7 +89,7 @@ name of a file to be read or written.
          itself. The available suboptions are listed on the individual 
          format pages.  We'll make an example from <xref linkend="fmt_kml" />:
        </para>
-         <para><command>gpsbabel -i gpx -f file.gpx -o kml,deficon="file://myicon.png",lines=0 -F one.kml -o kml -F two.kml</command></para>
+         <para><userinput>gpsbabel -i gpx -f file.gpx -o kml,deficon="file://myicon.png",lines=0 -F one.kml -o kml -F two.kml</userinput></para>
        <para>
        This command will read the GPX file <filename>file.gpx</filename>
        and create two KML files.    <filename>one.kml</filename> will
@@ -124,18 +124,18 @@ merged data to multiple destinations.
          <parameter moreinfo="none">-i</parameter> argument is seen.
          Files are read in the order they appear. So you could merge
          three input files into one output file with: </para>
-         <para><command>gpsbabel -i geo -f 1.loc -f 2.loc -f 3.loc -o geo -F big.loc</command></para>
+         <para><userinput>gpsbabel -i geo -f 1.loc -f 2.loc -f 3.loc -o geo -F big.loc</userinput></para>
          <para>You can merge files of different types:</para>
-         <para><command>gpsbabel  -i geo -f 1.loc -i gpx -f 2.gpx -i pcx 3.pcx  
--o gpsutil -F big.gps</command></para>
+         <para><userinput>gpsbabel  -i geo -f 1.loc -i gpx -f 2.gpx -i pcx 3.pcx  
+-o gpsutil -F big.gps</userinput></para>
          <para> You can write the same data in different output formats:</para>
-         <para><command>gpsbabel -i geo -f 1.loc -o gpx -F 1.gpx -o pcx 1.wpt</command></para>
+         <para><userinput>gpsbabel -i geo -f 1.loc -o gpx -F 1.gpx -o pcx 1.wpt</userinput></para>
          <para>If you want to change the character set of input or/and
          output side you can do this with the option <option>-c
          &lt;character set&gt;</option>. You can get a complete list
          of supported character sets with "gpsbabel -l".  To change
          the character set on both sides you should do this:</para>
-         <para><command>gpsbabel -i xcsv,style=foo.style -c latin1 -f foo -o xcsv,style=bar.style -c ms-ansi -F bar</command></para>
+         <para><userinput>gpsbabel -i xcsv,style=foo.style -c latin1 -f foo -o xcsv,style=bar.style -c ms-ansi -F bar</userinput></para>
          <para>Note, that some formats has a fixed character set and ignore this option.</para>
       </sect1>
       <sect1 id="Route_And_Track_Modes">
@@ -148,7 +148,7 @@ merged data to multiple destinations.
          waypoints, and is the default. So if you wanted to read all
          data from your unit into a gpx file, you might use a command
          like:</para>
-         <para><command> gpsbabel -t -r -w -i magellan -f com1:  -o gpx -F backup.gpx</command></para>
+         <para><userinput> gpsbabel -t -r -w -i magellan -f com1:  -o gpx -F backup.gpx</userinput></para>
          <para> Tracks and routes are advanced features and don't try
          to handle every possible hazard that can be encountered
          during a conversion.  If you're merging or converting files
@@ -253,7 +253,7 @@ merged data to multiple destinations.
       (i.e. wrapper applications using GPSBabel in the background). 
        The inifile mechanism can be disabled with an empty filename.
     </para>
-    <para><command>gpsbabel -p "" -i gpx -f something.gpx -o tiger -F -</command></para>
+    <para><userinput>gpsbabel -p "" -i gpx -f something.gpx -o tiger -F -</userinput></para>
 </sect1>
 <sect1 id="tracking">
   <title>Realtime tracking</title>
@@ -265,7 +265,7 @@ merged data to multiple destinations.
          inputs and KML is supported on output.   Additional formats 
          may be added by interested parties later.
     </para>
-    <para><command>gpsbabel -T -i garmin -f usb: -o kml -F xxx.kml</command></para>
+    <para><userinput>gpsbabel -T -i garmin -f usb: -o kml -F xxx.kml</userinput></para>
     <para>
          Will read the USB-connected Garmin and rewrite 'xxx.kml' atomically,
          suitable for a self-refreshing network link in Google Earth.
@@ -287,7 +287,7 @@ merged data to multiple destinations.
   Here is an example demonstrating segmenting a large command line
   by placing the input and filtering directives in a file called 'all_my_files'.
   </para>
-  <para><command>gpsbabel -b all_my_files -o gdb -F all_my_tracks.gdb</command></para>
+  <para><userinput>gpsbabel -b all_my_files -o gdb -F all_my_tracks.gdb</userinput></para>
   <para>
     'all_my_files' could look like this:
   </para>

diff --git a/xmldoc/filters/arc.xml b/xmldoc/filters/arc.xml
index 12aa7ae1b308a9dd972d8f8280094003a0b01da1..3b901a28e0d4687a7e754e6f941138e158d91891 100644 (file)
--- a/xmldoc/filters/arc.xml
+++ b/xmldoc/filters/arc.xml
@@ -37,6 +37,6 @@ Assuming the arc above is in a file called
 would include only points within one mile of the section of Lima Road 
 covered by the arc.
 </para>
-<para><command>gpsbabel -i geo -f 1.loc -x arc,file=lima_rd.txt,distance=1 -o mapsend -F 2.wpt</command></para>
+<para><userinput>gpsbabel -i geo -f 1.loc -x arc,file=lima_rd.txt,distance=1 -o mapsend -F 2.wpt</userinput></para>
 </example>
       

diff --git a/xmldoc/filters/discard.xml b/xmldoc/filters/discard.xml
index 09fdb4159cb4598d8fcead7bc013f5096373634e..82bd9bf902ecf3abb3dcd954e91d82757ebda6e4 100644 (file)
--- a/xmldoc/filters/discard.xml
+++ b/xmldoc/filters/discard.xml
@@ -6,7 +6,7 @@ for a given configuration of GPS satellites.
 </para>
 <example id="example_discard_filter">
 <title>Using the discard filter</title>
-<para><command> gpsbabel -i gpx -f in.gpx -x discard,hdop=10,vdop=20,hdopandvdop -o gpx -F out.gpx</command></para>
+<para><userinput> gpsbabel -i gpx -f in.gpx -x discard,hdop=10,vdop=20,hdopandvdop -o gpx -F out.gpx</userinput></para>
 </example>
 <para> Contributed by Tobias Minich.</para>
       

diff --git a/xmldoc/filters/duplicate.xml b/xmldoc/filters/duplicate.xml
index 450d9ed297f934f7b2d0535f51583dcf043c1b92..2d5558d3f5a889e81d340acbb4831eccff221606 100644 (file)
--- a/xmldoc/filters/duplicate.xml
+++ b/xmldoc/filters/duplicate.xml
@@ -15,6 +15,6 @@ Generally, at least one of these options is required.
   <link linkend="fmt_gpx">gpx</link> file that more than likely 
   contains only unique points and point data.
   </para>
-  <para><command> gpsbabel -i gpx -f 1.gpx -f 2.gpx -x duplicate,location,shortname -o gpx -F merged_with_no_dupes.gpx</command></para>
+  <para><userinput> gpsbabel -i gpx -f 1.gpx -f 2.gpx -x duplicate,location,shortname -o gpx -F merged_with_no_dupes.gpx</userinput></para>
 </example>
       

diff --git a/xmldoc/filters/interpolate.xml b/xmldoc/filters/interpolate.xml
index 453311ec31a42b675d77213b48b78304e674ac5c..5f5f5a16f2c0e72d8e09bfde2c61c8416d4b1b61 100644 (file)
--- a/xmldoc/filters/interpolate.xml
+++ b/xmldoc/filters/interpolate.xml
@@ -12,19 +12,19 @@ must specify either the
 This command line reads track.gpx and inserts points wherever two adjacent
 trackpoints are more than 10 seconds apart:
 </para>
-<para><command>gpsbabel -i gpx -f track.gpx -x interpolate,time=10 -o gpx -F newtrack.gpx</command></para>
+<para><userinput>gpsbabel -i gpx -f track.gpx -x interpolate,time=10 -o gpx -F newtrack.gpx</userinput></para>
 
 <para>
 This command reads track.gpx and inserts points wherever two adjacent
 trackpoints are more than 15 kilometers apart:
 </para>
 
-<para><command>gpsbabel -i gpx -f track.gpx -x interpolate,distance=15k -o gpx -F newtrack.gpx</command></para>
+<para><userinput>gpsbabel -i gpx -f track.gpx -x interpolate,distance=15k -o gpx -F newtrack.gpx</userinput></para>
 
 <para>
 This command reads track.gpx and inserts points wherever two adjacent
 trackpoints are more than 2 miles apart:
 </para>
 
-<para><command>gpsbabel -i gpx -f track.gpx -x interpolate,distance=2m -o gpx -F newtrack.gpx</command></para>
+<para><userinput>gpsbabel -i gpx -f track.gpx -x interpolate,distance=2m -o gpx -F newtrack.gpx</userinput></para>
 </example>      

diff --git a/xmldoc/filters/nuketypes.xml b/xmldoc/filters/nuketypes.xml
index 839760851e40c908908ef5153f44f5510861687a..21e9aa8fa3530d60be1078959b42c548d6ff171d 100644 (file)
--- a/xmldoc/filters/nuketypes.xml
+++ b/xmldoc/filters/nuketypes.xml
@@ -11,6 +11,6 @@ waypoints and you want a GPX file that contains only tracks,
 you may use this filter to remove the waypoints and the routes 
 with this command:
 </para>
-<para><command>gpsbabel -i gpx -f bigfile.gpx -x nuketypes,waypoints,routes -o gpx -F tracksonly.gpx</command></para>
+<para><userinput>gpsbabel -i gpx -f bigfile.gpx -x nuketypes,waypoints,routes -o gpx -F tracksonly.gpx</userinput></para>
 </example>
    

diff --git a/xmldoc/filters/options/duplicate-all.xml b/xmldoc/filters/options/duplicate-all.xml
index c85ec5b00ac5a3e68489cc8004a2906169ba1924..bdbcfab60a4fa51a79655d63eef9bb5c73950d8b 100644 (file)
--- a/xmldoc/filters/options/duplicate-all.xml
+++ b/xmldoc/filters/options/duplicate-all.xml
@@ -12,6 +12,6 @@ This option may be used to implement an "ignore list."  In the following
 example, the duplicate filter is used to remove a list of waypoints to be
 ignored from a larger collection of waypoints:
 </para>
-<para><command>gpsbabel -i gpx -f waypoints.gpx -i csv -f to_ignore.csv -x duplicate,shortname,all -o gpx -F filtered.gpx</command></para>
+<para><userinput>gpsbabel -i gpx -f waypoints.gpx -i csv -f to_ignore.csv -x duplicate,shortname,all -o gpx -F filtered.gpx</userinput></para>
 </example>
 

diff --git a/xmldoc/filters/options/duplicate-correct.xml b/xmldoc/filters/options/duplicate-correct.xml
index b66b6e90b7e6d36ff0040e3815882af635aa8284..8faefd5871636594766e0c8240270d19b0fb4a4b 100644 (file)
--- a/xmldoc/filters/options/duplicate-correct.xml
+++ b/xmldoc/filters/options/duplicate-correct.xml
@@ -11,7 +11,7 @@ geocaches in a Groundspeak pocket query:
 <example id="Correcting_Cache_Locations">
 <title>Using the duplicate filter to correct the locations of "puzzle"
 geocaches</title>
-<para><command>gpsbabel -i gpx -f 43622.gpx -i csv -f corrections.csv -x duplicate,shortname,correct -o gpx -F 43622-corrected.gpx</command></para>
+<para><userinput>gpsbabel -i gpx -f 43622.gpx -i csv -f corrections.csv -x duplicate,shortname,correct -o gpx -F 43622-corrected.gpx</userinput></para>
 <para>
 After this command is run, the waypoints in the output file will have all 
 of the descriptive information from <filename>43622.gpx</filename>, but 

diff --git a/xmldoc/filters/options/track-merge.xml b/xmldoc/filters/options/track-merge.xml
index 6d2e0d2a9bad8240196c4554da22c1e11d1e95a1..91b4cb3b97b455ba7184a8a8bb00c4c534c551cd 100644 (file)
--- a/xmldoc/filters/options/track-merge.xml
+++ b/xmldoc/filters/options/track-merge.xml
@@ -9,6 +9,6 @@ dropped.
 Suppose you want to merge tracks recorded with two different GPS devices 
 at the same time.  To do that, use this command line:
 </para>
-<para><command>gpsbabel -t -i gpx -f john.gpx -i gpx -f doe.gpx -x track,merge,title="COMBINED LOG" -o gpx -F john_doe.gpx</command></para>
+<para><userinput>gpsbabel -t -i gpx -f john.gpx -i gpx -f doe.gpx -x track,merge,title="COMBINED LOG" -o gpx -F john_doe.gpx</userinput></para>
 </example>
 

diff --git a/xmldoc/filters/options/track-move.xml b/xmldoc/filters/options/track-move.xml
index 6ba10c0cea922939013b7a66ecda338a33744ada..22452828aca50f485b3da20f5bff752e50590f2a 100644 (file)
--- a/xmldoc/filters/options/track-move.xml
+++ b/xmldoc/filters/options/track-move.xml
@@ -8,6 +8,6 @@ time zone.
 <para>
 The following command line will shift all tracks to be one hour later.
 </para>
-<para><command>gpsbabel -t -i gpx -f in.gpx -x track,move=+1h -o gpx -F out.gpx</command></para>
+<para><userinput>gpsbabel -t -i gpx -f in.gpx -x track,move=+1h -o gpx -F out.gpx</userinput></para>
 </example>
 

diff --git a/xmldoc/filters/options/track-sdistance.xml b/xmldoc/filters/options/track-sdistance.xml
index 35313095dabb9e2940e83de38b2a7c59954052b5..73fb4462cee252bf4f45a53cd727e4a4446963af 100644 (file)
--- a/xmldoc/filters/options/track-sdistance.xml
+++ b/xmldoc/filters/options/track-sdistance.xml
@@ -10,12 +10,12 @@
 
          <para> For example, to split the track if the distance between
          points is greater than 100 meters, use this:</para>
-         <para><command>
+         <para><userinput>
 gpsbabel -t 
      -i gpx -f in.gpx 
      -x track,pack,sdistance=0.1k" 
      -o gpx -F out.gpx
-</command></para>
+</userinput></para>
         <para> The sdistance option can be combined with the split option.
         The track then will be split only if both time and distance
         interval exceeds the supplied values. This technique can be used to 
@@ -26,11 +26,11 @@ gpsbabel -t
         This example splits the track
         if the device is without signal for at least 5 minutes
         and during this time moves more than 300 meters:</para>
-        <para><command>
+        <para><userinput>
 gpsbabel -t \
      -i gpx -f in.gpx \
      -x track,pack,sdistance=0.3k,split=5m \
      -o gpx -F out.gpx
-</command></para>
+</userinput></para>
 
 

diff --git a/xmldoc/filters/options/track-split.xml b/xmldoc/filters/options/track-split.xml
index 8f93ff155b8a5df93d0707b8e260ca2d5556d66d..b8df748f1274d2487f753b9ec871ccf6d9010db8 100644 (file)
--- a/xmldoc/filters/options/track-split.xml
+++ b/xmldoc/filters/options/track-split.xml
@@ -4,12 +4,12 @@
          split a single tracks into separate tracks for each day and
          name them, use this:
       </para>
-         <para><command> gpsbabel -t -i gpx -f in.gpx -x track,split,title="ACTIVE LOG # %Y%m%d" -o gpx -F out.gpx</command></para>
+         <para><userinput> gpsbabel -t -i gpx -f in.gpx -x track,split,title="ACTIVE LOG # %Y%m%d" -o gpx -F out.gpx</userinput></para>
          <para> If the input has multiple tracks, pack them together before
 splitting them back apart per day thusly: </para>
-         <para><command>           gpsbabel -t   -i gpx -f in.gpx  
+         <para><userinput>                 gpsbabel -t   -i gpx -f in.gpx  
      -x track,pack,split,title="ACTIVE LOG # %D"       
-     -o gpx -F out.gpx</command></para>
+     -o gpx -F out.gpx</userinput></para>
          <para> Additionally you can add an interval to the split
          option.  With this the track will be split if the time
          between two points is greater than this parameter. The
@@ -20,9 +20,9 @@ splitting them back apart per day thusly: </para>
 </para>
          <para> For example, to split a track based on an four hour
          interval, use this:</para>
-         <para><command>            
+         <para><userinput>            
 gpsbabel -t 
      -i gpx -f in.gpx 
      -x track,pack,split=4h,title="LOG # %c" 
      -o gpx -F out.gpx
-</command></para>
+</userinput></para>

diff --git a/xmldoc/filters/options/track-start.xml b/xmldoc/filters/options/track-start.xml
index 06c22ccb28390eb61cd572cc37e2befe500e34b8..143e05d22d5a47c845646e8d11a31d29d7701b38 100644 (file)
--- a/xmldoc/filters/options/track-start.xml
+++ b/xmldoc/filters/options/track-start.xml
@@ -20,5 +20,5 @@ given date, you need not specify the minutes or seconds.
 To get only the parts of a track that were mapped on 20 July 2005
 between 10 AM and 6 PM, use this command line:
 </para> 
-<para><command>gpsbabel -t -i gpx -f in.gpx -x track,start=2005072010,stop=2005072018 -o gpx -F out.gpx </command></para>
+<para><userinput>gpsbabel -t -i gpx -f in.gpx -x track,start=2005072010,stop=2005072018 -o gpx -F out.gpx </userinput></para>
 </example>

diff --git a/xmldoc/filters/options/transform-del.xml b/xmldoc/filters/options/transform-del.xml
index 9aa4e47da6dd3979044a679a4e21daf2f0e081a0..46b78d6bb5f0b8f6da88b9d1f7397aeafe6ef266 100644 (file)
--- a/xmldoc/filters/options/transform-del.xml
+++ b/xmldoc/filters/options/transform-del.xml
@@ -5,5 +5,5 @@ you are trying to avoid duplicated data in the output.
 </para>
 <example id="transform_del">
 <title>Convert a GPX track to GPX waypoints, tossing the original track</title>
-<para><command>gpsbabel -i gpx -f blah.gpx -x transform,wpt=trk,del -o gpx -F converted.gpx</command></para>
+<para><userinput>gpsbabel -i gpx -f blah.gpx -x transform,wpt=trk,del -o gpx -F converted.gpx</userinput></para>
 </example>

diff --git a/xmldoc/filters/options/transform-rte.xml b/xmldoc/filters/options/transform-rte.xml
index 631ec4251e6f388653db894e3cb08531bc098eae..4382e0f5b3bcf2b2064ec9612e8bdb7b313ada05 100644 (file)
--- a/xmldoc/filters/options/transform-rte.xml
+++ b/xmldoc/filters/options/transform-rte.xml
@@ -7,5 +7,5 @@ This option selects the destination type of this filter to be routes.  Choose th
 Say you you have a data file that came from CSV file that you want to convert  
 to a GPX route that can be loaded into Mapsource.  Use the following command:
 </para>
-<para><command>gpsbabel -i csv -f blah.txt -x transform,rte=wpt -o gdb -F blah.gdb</command></para>
+<para><userinput>gpsbabel -i csv -f blah.txt -x transform,rte=wpt -o gdb -F blah.gdb</userinput></para>
 </example>

diff --git a/xmldoc/filters/options/transform-trk.xml b/xmldoc/filters/options/transform-trk.xml
index 8a72a27b5e2a4a34e7f6f60fb450e06e24d8d5ec..d17d98b9ffddfcdd351228f4560619c8c6709cdd 100644 (file)
--- a/xmldoc/filters/options/transform-trk.xml
+++ b/xmldoc/filters/options/transform-trk.xml
@@ -9,5 +9,5 @@ A single track will be created in the sequence they appear in the input.
 Say you you have a data file that came from CSV file that you want to convert  
 to a GPX track that can be loaded into Mapsource.  Use the following command:
 </para>
-<para><command>gpsbabel -i csv -f blah.txt -x transform,trk=wpt -o gdb -F blah.gdb</command></para>
+<para><userinput>gpsbabel -i csv -f blah.txt -x transform,trk=wpt -o gdb -F blah.gdb</userinput></para>
 </example>

diff --git a/xmldoc/filters/options/transform-wpt.xml b/xmldoc/filters/options/transform-wpt.xml
index 1399f0fb05a8eeb2b9609ee9e16884922526fbdd..513b5ef0716f2c2a72e190da33c0a967d5ec7492 100644 (file)
--- a/xmldoc/filters/options/transform-wpt.xml
+++ b/xmldoc/filters/options/transform-wpt.xml
@@ -7,5 +7,5 @@ Choose this when you want to convert tracks or routes into waypoints.
 <para>
 Say you you have a KML file that contains a track but you want to convert it to a CSV file that can contain only waypoints, perhaps to import into a spreadsheet.  Use the following command:
 </para>
-<para><command>gpsbabel -i kml -f blah.kml -x transform,wpt=trk -o csv -F blah.txt</command></para>
+<para><userinput>gpsbabel -i kml -f blah.kml -x transform,wpt=trk -o csv -F blah.txt</userinput></para>
 </example>

diff --git a/xmldoc/filters/polygon.xml b/xmldoc/filters/polygon.xml
index 5b5bb63cf3ff1097cb0eb78867782dffab70da48..ddf2699f6a3607a79fb3363fa8b568d2ebfec6b7 100644 (file)
--- a/xmldoc/filters/polygon.xml
+++ b/xmldoc/filters/polygon.xml
@@ -48,7 +48,7 @@ Suppose you have a polygon file that defines the border of your county,
 called mycounty.txt.  This command line will give you only the points 
 in your county:
 </para>
-<para><command>gpsbabel -i geo -f 1.loc -x polygon,file=mycounty.txt -o mapsend -F 2.wpt</command></para>
+<para><userinput>gpsbabel -i geo -f 1.loc -x polygon,file=mycounty.txt -o mapsend -F 2.wpt</userinput></para>
 </example>
 <example id="example_in_or_close_to">
 <title>Using the polygon and arc filters to find points in or nearly in a 
@@ -61,11 +61,11 @@ boundaries of your polygon are not quite perfect, so you want to provide a
 buffer zone around it in case there are points nearby that should be in the 
 polygon but aren't quite.
 </para>
-<para><command>
+<para><userinput>
 gpsbabel -i gpx -f points.gpx -x stack,push -x polygon,file=mycounty.txt 
 -x stack,swap -x arc,file=mycounty.txt,distance=1k -x stack,pop,append 
 -x duplicate,shortname -o gpx -F nearmycounty.gpx
-</command></para>
+</userinput></para>
 <para>
 This command makes a copy of the points, finds the ones that are in your
 your county, swaps that result with the copy of the original set of points,

diff --git a/xmldoc/filters/position.xml b/xmldoc/filters/position.xml
index 4bf0869c173df90e8519397e02046a8268308570..01df222c717121f98cd5ada5f8ee832e2c312572 100644 (file)
--- a/xmldoc/filters/position.xml
+++ b/xmldoc/filters/position.xml
@@ -10,6 +10,6 @@ has come before.
 The following command removes multiple points that are within 
 one foot of each other, leaving just one.
 </para>
-<para><command>gpsbabel -i geo -f 1.loc -f 2.loc -x position,distance=1f -o mapsend -F 3.wpt</command></para>
+<para><userinput>gpsbabel -i geo -f 1.loc -f 2.loc -x position,distance=1f -o mapsend -F 3.wpt</userinput></para>
 </example>
       

diff --git a/xmldoc/filters/radius.xml b/xmldoc/filters/radius.xml
index 607f97e5969d1c62c0624e6411ce5a0c15249188..1e3f4ffd78cf13caad79d97f75c67546818c6252 100644 (file)
--- a/xmldoc/filters/radius.xml
+++ b/xmldoc/filters/radius.xml
@@ -12,6 +12,6 @@ center appear earlier in the output file.
  <para>This example command line would include only points within 1 1/2 miles
        of N30.000 W 90.000</para>
 
-<para><command>gpsbabel -i geo -f 1.loc -x radius,distance=1.5M,lat=30.0,lon=-90.0 -o mapsend -F 2.wpt</command></para>
+<para><userinput>gpsbabel -i geo -f 1.loc -x radius,distance=1.5M,lat=30.0,lon=-90.0 -o mapsend -F 2.wpt</userinput></para>
 </example>
       

diff --git a/xmldoc/filters/simplify.xml b/xmldoc/filters/simplify.xml
index 1c6f47938470604f5519a76b0e81aa739b519e38..026551bc0ffe00aa3ff71cc53a147769f2ed4e6d 100644 (file)
--- a/xmldoc/filters/simplify.xml
+++ b/xmldoc/filters/simplify.xml
@@ -17,5 +17,5 @@ For example, suppose you have a route from Street Atlas 2003 that you
 wish to use with a Magellan GPS receiver that only supports up to 50 points 
 in a route:
 </para>
-<para><command>gpsbabel -r -i saroute -f RoadTrip.anr -x simplify,count=50 -o magellan  -F grocery.rte</command></para>
+<para><userinput>gpsbabel -r -i saroute -f RoadTrip.anr -x simplify,count=50 -o magellan  -F grocery.rte</userinput></para>
       

diff --git a/xmldoc/filters/stack.xml b/xmldoc/filters/stack.xml
index 40d30e75fdfaae075732a24efa20fde3146fdc70..8330123558b4932778f4ceeacfdafe64dc1280da 100644 (file)
--- a/xmldoc/filters/stack.xml
+++ b/xmldoc/filters/stack.xml
@@ -21,7 +21,7 @@ can fit in your computer's memory.
  duplicates can be removed with the DUPLICATE filter; see
  above.)
 </para>
-         <para><command>           
+         <para><userinput>           
 gpsbabel -i gpx -f in.gpx 
          -x stack,push,copy 
          -x polygon,file=county_a.txt 
@@ -29,13 +29,13 @@ gpsbabel -i gpx -f in.gpx
          -x polygon,file=county_b.txt 
          -x stack,pop,append 
          -o gpx -F out.gpx
-</command></para>
+</userinput></para>
          <para> This example reads a large list of waypoints and
          extracts the points within 20 miles of each of two cities,
          writing the waypoint descriptions into two different PalmDoc
          files and exporting all of the points to the GPS receiver:
 </para>
-         <para><command>           
+         <para><userinput>           
 gpsbabel -i gpx -f indiana.gpx 
          -x stack,push,copy 
          -x radius,lat=41.0765,lon=-85.1365,distance=20m 
@@ -45,5 +45,5 @@ gpsbabel -i gpx -f indiana.gpx
          -o palmdoc,dbname=Indianapolis -F indianapolis.pdb 
          -x stack,pop,append 
          -o magellan -F fwaind.wpt
-</command></para>
+</userinput></para>
       

diff --git a/xmldoc/filters/transform.xml b/xmldoc/filters/transform.xml
index 7a55f3e9182dcbc10b9b477e3e0f46e8713c1366..ddb82ca11fc09273763387630712f635b49c7adc 100644 (file)
--- a/xmldoc/filters/transform.xml
+++ b/xmldoc/filters/transform.xml
@@ -10,7 +10,7 @@
 <para>
   The following example show you how to create a route from a waypoint table.
 </para>
-  <para><command>gpsbabel -i csv waypts.txt -x transform,rte=wpt -o gpx -F route.gpx</command></para>
+  <para><userinput>gpsbabel -i csv waypts.txt -x transform,rte=wpt -o gpx -F route.gpx</userinput></para>
 <para>
   Only the first letter of option value decides which transformation will be done.
   Depending on the used option it can be only 'W' for waypoints, 'R' for routes or

diff --git a/xmldoc/formats/an1.xml b/xmldoc/formats/an1.xml
index 466fb5cd3edffed3604d1e19bf55ba97dac63c4f..96ee1443552b66f9aa215bd102e0b6640632ff43 100644 (file)
--- a/xmldoc/formats/an1.xml
+++ b/xmldoc/formats/an1.xml
@@ -7,7 +7,7 @@ thick red lines for routes or tracks.  It is possible to merge two drawing
 layers by doing something like this:
 </para>
 
-<para><command>gpsbabel -i an1 -f one.an1 -f two.an1 -o an1 -F merged.an1</command></para>
+<para><userinput>gpsbabel -i an1 -f one.an1 -f two.an1 -o an1 -F merged.an1</userinput></para>
 
 <para> 
 In this case, the merged data will contain all of the

diff --git a/xmldoc/formats/bcr.xml b/xmldoc/formats/bcr.xml
index 1542994c36bed5e0524ba8ad66dae0b880bd6b64..76915df696b22cbc73936386cddd6fdd40b91c66 100644 (file)
--- a/xmldoc/formats/bcr.xml
+++ b/xmldoc/formats/bcr.xml
@@ -16,6 +16,6 @@ reports are welcome.
 </para>
 <example id="sample_bcr_command">
   <title>Sample BCR command with all options</title>
-  <para><command>gpsbabel -r -i gpx -f in.gpx -o bcr,index=1,name="From A to B",radius=6371012 -F a_to_b.bcr</command></para>
+  <para><userinput>gpsbabel -r -i gpx -f in.gpx -o bcr,index=1,name="From A to B",radius=6371012 -F a_to_b.bcr</userinput></para>
 </example>
     

diff --git a/xmldoc/formats/garmin.xml b/xmldoc/formats/garmin.xml
index fbdf33fb1a994ec738c57a5ca4bda8dc26c891d2..4c1756d7109b99cb13f1baf90b9953d1128ae6e7 100644 (file)
--- a/xmldoc/formats/garmin.xml
+++ b/xmldoc/formats/garmin.xml
@@ -123,7 +123,7 @@
        them to a GPX file:
 </para>
 
-      <para><command>gpsbabel -i garmin -f usb: -o gpx -F blah.gpx</command></para>
+      <para><userinput>gpsbabel -i garmin -f usb: -o gpx -F blah.gpx</userinput></para>
 
 <para>
        If you have multiple units attached via USB, you may provide 
@@ -132,7 +132,7 @@
        "usb:0", "usb:1", and "usb:2".  To get a list of recognized devices,
        specifiy a negative number such as:
 </para>
-       <para><command>gpsbabel -i garmin -f usb:-1</command></para>
+       <para><userinput>gpsbabel -i garmin -f usb:-1</userinput></para>
  
 <para> 
 When reporting problems with the Garmin format, be sure to include
@@ -140,7 +140,7 @@ the full unit model, firmware version, and be prepared to offer
 debugging dumps by adding "-D9" to the command line, like:
 </para>
 
-      <para><command> gpsbabel -D9 -i garmin -f usb: -o gpx -F blah.gpx</command></para>
+      <para><userinput> gpsbabel -D9 -i garmin -f usb: -o gpx -F blah.gpx</userinput></para>
 
 <para> 
 Custom icons are supported on units that support that.

diff --git a/xmldoc/formats/garmin_txt.xml b/xmldoc/formats/garmin_txt.xml
index 06288ceef030688d1ebdd7197c28ae19d85a87ac..b9a9c88d18229cbfeb320af4e459ca5bd29b3127 100644 (file)
--- a/xmldoc/formats/garmin_txt.xml
+++ b/xmldoc/formats/garmin_txt.xml
@@ -18,6 +18,6 @@ be solved with the 'date' and 'time' options.
 </para>
 <example id="all_garmin_txt_options">
   <title>Command showing garmin_txt output with all options</title>
-  <para><command>gpsbabel -i garmin_txt,date="MM/DD/YYYY",time="hh:mm:ss xx" -f in.txt -o garmin_txt,date="DD.MM.YYYY",datum="WGS 72",dist=m,prec=6,temp=c,time="HH:mm:ss",utc=+2 -F out.txt</command></para>
+  <para><userinput>gpsbabel -i garmin_txt,date="MM/DD/YYYY",time="hh:mm:ss xx" -f in.txt -o garmin_txt,date="DD.MM.YYYY",datum="WGS 72",dist=m,prec=6,temp=c,time="HH:mm:ss",utc=+2 -F out.txt</userinput></para>
 </example>
     

diff --git a/xmldoc/formats/html.xml b/xmldoc/formats/html.xml
index 0589fabad6650c488952cadd7b148b0b481e6080..211da87ff0a91e17e16653ed091cbc713ad17be8 100644 (file)
--- a/xmldoc/formats/html.xml
+++ b/xmldoc/formats/html.xml
@@ -12,5 +12,5 @@ for Geocachers with pocket queries.
 Groundspeak extensions and writes an HTML file with encrypted hints
 that is rendered using a custom stylesheet:
 </para>
-<para><command>gpsbabel -i gpx -f 12345.gpx -o html,stylesheet=green.css,encrypt -F 12345.html</command></para>
+<para><userinput>gpsbabel -i gpx -f 12345.gpx -o html,stylesheet=green.css,encrypt -F 12345.html</userinput></para>
     

diff --git a/xmldoc/formats/igc.xml b/xmldoc/formats/igc.xml
index 8a900efd3d94df56ca7b91bd21b6d2ab4b554b83..57e330b133b7a9095435679e06eb509a31a38967 100644 (file)
--- a/xmldoc/formats/igc.xml
+++ b/xmldoc/formats/igc.xml
@@ -42,7 +42,7 @@ will not be accepted as proof of a flight.
 A track stored in another format (GPX for example) representing a recorded
 flight can be converted into an IGC file:
 </para>
-<para><command>gpsbabel -i gpx -f mytrk.gpx -o igc -F myflight.igc</command></para>
+<para><userinput>gpsbabel -i gpx -f mytrk.gpx -o igc -F myflight.igc</userinput></para>
 <para>
 If multiple track segments are provided in the input file, the one with the
 most points will be used.
@@ -51,34 +51,34 @@ most points will be used.
 A route stored in another format representing a task declaration can be
 converted into an IGC file:
 </para>
-<para><command>gpsbabel -i gpx -f myrte.gpx -o igc -F mytask.igc</command></para>
+<para><userinput>gpsbabel -i gpx -f myrte.gpx -o igc -F mytask.igc</userinput></para>
 <para>
 A route and a track in other formats can be included into a single IGC file:
 </para>
-<para><command>gpsbabel -i gpx -f mytrk.gpx -f myrte.gpx -o igc -F myflight.igc</command></para>
+<para><userinput>gpsbabel -i gpx -f mytrk.gpx -f myrte.gpx -o igc -F myflight.igc</userinput></para>
 <para>
 A similar result can be obtained by downloading the track log and routes
 directly from a GPS device connected to a PC.  For example to create an IGC
 file from data recorded in a Garmin GPS connected to the first serial port of
 a PC running Linux:
 </para>
-<para><command>gpsbabel -t -r -i garmin -f /dev/ttyS0 -o igc -F myflight.igc</command></para>
+<para><userinput>gpsbabel -t -r -i garmin -f /dev/ttyS0 -o igc -F myflight.igc</userinput></para>
 <para>
 For Windows operating systems:
 </para>
-<para><command>gpsbabel -t -r -i garmin -f com1 -o igc -F myflight.igc</command></para>
+<para><userinput>gpsbabel -t -r -i garmin -f com1 -o igc -F myflight.igc</userinput></para>
 <para>
 A waypoint file in another format containing a waypoint whose short name is
 "PILOT" can be merged into an IGC file.  The description field of the waypoint
 will be used for the pilot name in the IGC file header:
 </para>
-<para><command>gpsbabel -i gpx -f mytrk.gpx -f myrte.gpx -f mywpt.gpx -o igc -F myflight.igc
-gpsbabel -w -t -r -i garmin -f /dev/ttyS0 -o igc -F myflight.igc</command></para>
+<para><userinput>gpsbabel -i gpx -f mytrk.gpx -f myrte.gpx -f mywpt.gpx -o igc -F myflight.igc
+gpsbabel -w -t -r -i garmin -f /dev/ttyS0 -o igc -F myflight.igc</userinput></para>
 <para>
 Some formats such as GPX allow routes, tracks and waypoints to exist in the
 same file and can be used to fully populate an IGC file:
 </para>
-<para><command>gpsbabel -i gpx -f myall.gpx -o igc -F myflight.igc</command></para>
+<para><userinput>gpsbabel -i gpx -f myall.gpx -o igc -F myflight.igc</userinput></para>
 </section>
 
 <section id="fmt_igc_convfrom">
@@ -88,11 +88,11 @@ Data in an IGC file can be converted into other formats.  For example to
 generate OziExplorer files containing tracks representing the recorded
 flight (myozi.plt) and routes representing declared tasks (myozi.rte):
 </para>
-<para><command>gpsbabel -i igc -f myflight.igc -o ozi -F myozi</command></para>
+<para><userinput>gpsbabel -i igc -f myflight.igc -o ozi -F myozi</userinput></para>
 <para>
 Or to GPX format:
 </para>
-<para><command>gpsbabel -i igc -f myflight.igc -o gpx -F myflight.gpx</command></para>
+<para><userinput>gpsbabel -i igc -f myflight.igc -o gpx -F myflight.gpx</userinput></para>
 <para>
 Header information from the IGC file will be written to the description field
 of the track(s).
@@ -110,23 +110,23 @@ tracks.  The latitude, longitude and timestamps in the tracks will be identical.
 A route stored in another format can be merged with an existing IGC file that
 has no task declaration, to generate a new IGC file with a task declaration:
 </para>
-<para><command>gpsbabel -i igc -f myflight.igc -i gpx -f myrte.gpx -o igc -F mynew.igc</command></para>
+<para><userinput>gpsbabel -i igc -f myflight.igc -i gpx -f myrte.gpx -o igc -F mynew.igc</userinput></para>
 <para>
 A two dimensional (lat/lon) track recorded during a flight by a GPS receiver
 can be merged with a one dimensional (altitude) track recorded during the same
 flight by a barograph instrument.  The result is a three dimensional IGC file
 representing the flight:
 </para>
-<para><command>gpsbabel -i gpx -f baro.gpx -i igc -f my2D.igc -o igc -F my3D.igc</command></para>
+<para><userinput>gpsbabel -i gpx -f baro.gpx -i igc -f my2D.igc -o igc -F my3D.igc</userinput></para>
 <para>
 The same can be acheived by downloading directly from a barograph instrument
 supported by GPSBabel.  For example with a Brauniger IQ Comp GPS variometer:
 </para>
-<para><command>gpsbabel -i baroiq -f /dev/ttyS0 -i igc -f my2D.igc -o igc,timeadj=auto -F my3D.igc</command></para>
+<para><userinput>gpsbabel -i baroiq -f /dev/ttyS0 -i igc -f my2D.igc -o igc,timeadj=auto -F my3D.igc</userinput></para>
 <para>
 or:
 </para>
-<para><command>gpsbabel -i baroiq -f com1 -i igc -f my2D.igc -o igc,timeadj=auto -F my3D.igc</command></para>
+<para><userinput>gpsbabel -i baroiq -f com1 -i igc -f my2D.igc -o igc,timeadj=auto -F my3D.igc</userinput></para>
 <para>
 (Documentation contributed by Chris Jones, Aug 2004)
 </para>

diff --git a/xmldoc/formats/magnav.xml b/xmldoc/formats/magnav.xml
index b7ddeed082158a3c86f81330f93d2c5effe472d4..76511170529b0384f55065e65e63a28cb55a9e56 100644 (file)
--- a/xmldoc/formats/magnav.xml
+++ b/xmldoc/formats/magnav.xml
@@ -27,7 +27,7 @@ PalmOS, not of NAV Companion.)
 <para>
 To merge the databases, use a command line like the following:
 </para>
-<para><command>gpsbabel -i magnav -f Companion_Waypoints.PDB -i geo -f geocaching.loc -o magnav -F merged.pdb</command></para>
+<para><userinput>gpsbabel -i magnav -f Companion_Waypoints.PDB -i geo -f geocaching.loc -o magnav -F merged.pdb</userinput></para>
 <para>
 Second, you must use the installer to install your new PDB file.  Don't
 make the mistake of copying it over the existing Companion_Waypoints.PDB

diff --git a/xmldoc/formats/mapconverter.xml b/xmldoc/formats/mapconverter.xml
index 3531af7c4816d125b07262361513c784caad6646..3c9fa9dabd3e0a6b8ee007d36655ed24126af5a8 100644 (file)
--- a/xmldoc/formats/mapconverter.xml
+++ b/xmldoc/formats/mapconverter.xml
@@ -14,7 +14,7 @@ The steps for using GPSBabel and Mapconverter go something like this:
 <para>
 Step 1: Create a mapconverter file using gpsbabel.
 </para>
-<para><command>gpsbabel -i geo -f geocaching.loc -o mapconverter -F foo.txt</command></para>
+<para><userinput>gpsbabel -i geo -f geocaching.loc -o mapconverter -F foo.txt</userinput></para>
 <para>
 Step 2: Launch mapconverter.exe and choose foo.txt as your input file.
        Click the begin button to have mapconverter process foo.txt.

diff --git a/xmldoc/formats/openoffice.xml b/xmldoc/formats/openoffice.xml
index 03f35131a79dc22a3684f67970f113adba026950..56d50f1c01614d57533a37ff6e6d057cb91e273c 100644 (file)
--- a/xmldoc/formats/openoffice.xml
+++ b/xmldoc/formats/openoffice.xml
@@ -5,7 +5,7 @@
 format.  Intended to serve as source for number-processing
 applications like OpenOffice, Ploticus and others. Tab was chosen as
 delimiter because it is a) supported by both OpenOffice and Ploticus
-and b) is not ',', so you can use <command moreinfo="none">sed -i
-"s/./,/g" &lt;x&gt;.csv'</command> to adapt it to locales where ',' is
+and b) is not ',', so you can use <userinput moreinfo="none">sed -i
+"s/./,/g" &lt;x&gt;.csv'</userinput> to adapt it to locales where ',' is
 used as decimal seperator.  Contributed by Tobias Minich.</para>
     

diff --git a/xmldoc/formats/options/an1-nogc.xml b/xmldoc/formats/options/an1-nogc.xml
index e2c9288a0cebb5ffd7a5e70f368a28d55e623128..2dfa4c589384d3d545b5bf8210b8461df0354224 100644 (file)
--- a/xmldoc/formats/options/an1-nogc.xml
+++ b/xmldoc/formats/options/an1-nogc.xml
@@ -4,5 +4,5 @@ difficulty and terrain, GPSBabel will automatically include that information
 in the waypoint descriptions in the generated drawing file.  If you do not 
 want that, specify the "nogc" option on the command line:
 </para>
-<para><command>gpsbabel -i gpx -f 12345.gpx -o an1,nogc -F 12345.an1</command></para>
+<para><userinput>gpsbabel -i gpx -f 12345.gpx -o an1,nogc -F 12345.an1</userinput></para>
 

diff --git a/xmldoc/formats/options/bcr-index.xml b/xmldoc/formats/options/bcr-index.xml
index 164412e05fc0ba767b25a5b3e4360f41f954127d..2e960277da67e62116fff519b7ca1b5075c2fc74 100644 (file)
--- a/xmldoc/formats/options/bcr-index.xml
+++ b/xmldoc/formats/options/bcr-index.xml
@@ -5,5 +5,5 @@ routes read from a more expressive format.  If you have, say, a
 <link linkend="fmt_gpx">gpx</link> file that contains two routes, you may
 use this option to write them one at a time to individual files.
 </para>
-<para><command>gpsbabel -i gpx -f routes.gpx -o bcr,index=1 -F route1.bcr -o bcr,index=2 -F route2.bcr</command></para>
+<para><userinput>gpsbabel -i gpx -f routes.gpx -o bcr,index=1 -F route1.bcr -o bcr,index=2 -F route2.bcr</userinput></para>
 

diff --git a/xmldoc/formats/options/compegps-index.xml b/xmldoc/formats/options/compegps-index.xml
index 915db8f7e14b4d67a1fe24cc55af968a297de2e8..b82e931dd914f6715da4f6355d58022db9dd9c04 100644 (file)
--- a/xmldoc/formats/options/compegps-index.xml
+++ b/xmldoc/formats/options/compegps-index.xml
@@ -5,4 +5,4 @@ tracks read from a more expressive format.  If you have, say, a
 <link linkend="fmt_gpx">gpx</link> file that contains two routes, you may
 use this option to write them one at a time to individual files.
 </para>
-<para><command>gpsbabel -i gpx -f routes.gpx -o compegps,index=1 -F route1.txt -o compegps,index=2 -F route2.txt</command></para>
+<para><userinput>gpsbabel -i gpx -f routes.gpx -o compegps,index=1 -F route1.txt -o compegps,index=2 -F route2.txt</userinput></para>

diff --git a/xmldoc/formats/options/garmin-get_posn.xml b/xmldoc/formats/options/garmin-get_posn.xml
index 7d93bab7fbb38548c4648d829bb51b3ea2c4aaa3..b7baac3b6251d216d597311f79988ba7b71a8aa7 100644 (file)
--- a/xmldoc/formats/options/garmin-get_posn.xml
+++ b/xmldoc/formats/options/garmin-get_posn.xml
@@ -2,4 +2,4 @@
 and returns it as a single waypoint for further processing.  For example,
 to return the current position from a USB Garmin to a KML file:
 </para>
-<para><command>gpsbabel -i garmin,get_posn -f usb: -o kml -F myposition.kml</command></para>
+<para><userinput>gpsbabel -i garmin,get_posn -f usb: -o kml -F myposition.kml</userinput></para>

diff --git a/xmldoc/formats/options/garmin-power_off.xml b/xmldoc/formats/options/garmin-power_off.xml
index 145e7cf7a29956d4cad6780924347476d4b7815b..0c1b945fc6179d201a12a64ec335b1287b5b4eda 100644 (file)
--- a/xmldoc/formats/options/garmin-power_off.xml
+++ b/xmldoc/formats/options/garmin-power_off.xml
@@ -5,4 +5,4 @@ a unit that supports it is rather futile, so place this option carefully
 in your command.
 
 </para>
-<para><command>gpsbabel -o garmin,power_off -F /dev/ttyS0</command></para>
+<para><userinput>gpsbabel -o garmin,power_off -F /dev/ttyS0</userinput></para>

diff --git a/xmldoc/formats/options/igc-timeadj.xml b/xmldoc/formats/options/igc-timeadj.xml
index ceeb749cabecae36a6fa446d834bce3cb821ce8c..eb345d9b8209fdedbc70e10dec8e2b7b33f8b4a4 100644 (file)
--- a/xmldoc/formats/options/igc-timeadj.xml
+++ b/xmldoc/formats/options/igc-timeadj.xml
@@ -5,12 +5,12 @@ not correlating correctly.  This can be corrected manually by passing the time
 difference in seconds between the two time domains through the "timeadj"
 parameter.  This can be any positive or negative integer:
 </para>
-<para><command>gpsbabel -i gpx -f baro.gpx -i igc -f my2D.igc -o igc,timeadj=27 -F my3D.igc</command></para>
+<para><userinput>gpsbabel -i gpx -f baro.gpx -i igc -f my2D.igc -o igc,timeadj=27 -F my3D.igc</userinput></para>
 <para>
 GPSBabel can also attempt to deduce the time difference automatically.  This
 is done by comparing the time that it thinks that you landed on the GPS track
 and the barograph and adjusting accordingly:
 </para>
-<para><command>gpsbabel -i gpx -f baro.gpx -i igc -f my2D.igc -o igc,timeadj=auto -F my3D.igc</command></para>
+<para><userinput>gpsbabel -i gpx -f baro.gpx -i igc -f my2D.igc -o igc,timeadj=auto -F my3D.igc</userinput></para>
 
 

diff --git a/xmldoc/formats/options/ignrando-index.xml b/xmldoc/formats/options/ignrando-index.xml
index fb06f1d79615374c1ac8c7341079e26d91a61af7..f61f0e79095f9ba5e6fc8253ecafd68ae99c0a62 100644 (file)
--- a/xmldoc/formats/options/ignrando-index.xml
+++ b/xmldoc/formats/options/ignrando-index.xml
@@ -5,5 +5,5 @@ tracks read from a more expressive format.  If you have, say, a
 <link linkend="fmt_gpx">gpx</link> file that contains two tracks, you may
 use this option to write them one at a time to individual files.
 </para>
-<para><command>gpsbabel -i gpx -f tracks.gpx -o ignrando,index=1 -F track1.txt -o ignrando,index=2 -F track2.txt</command></para>
+<para><userinput>gpsbabel -i gpx -f tracks.gpx -o ignrando,index=1 -F track1.txt -o ignrando,index=2 -F track2.txt</userinput></para>
 

diff --git a/xmldoc/formats/options/nmn4-index.xml b/xmldoc/formats/options/nmn4-index.xml
index 25aacb215acb8f317fec65daf06512358c3c5fe1..e5fa3f10358e1b7b0121645c7b65487665fcf171 100644 (file)
--- a/xmldoc/formats/options/nmn4-index.xml
+++ b/xmldoc/formats/options/nmn4-index.xml
@@ -5,5 +5,5 @@ routes read from a more expressive format.  If you have, say, a
 <link linkend="fmt_gpx">gpx</link> file that contains two routes, you may
 use this option to write them one at a time to individual files.
 </para>
-<para><command>gpsbabel -i gpx -f routes.gpx -o nmn4,index=1 -F route1.rte -o nmn4,index=2 -F route2.rte</command></para>
+<para><userinput>gpsbabel -i gpx -f routes.gpx -o nmn4,index=1 -F route1.rte -o nmn4,index=2 -F route2.rte</userinput></para>
 

diff --git a/xmldoc/formats/options/stmsdf-index.xml b/xmldoc/formats/options/stmsdf-index.xml
index 1318ee7750e3f87d84e5b34658ebcc7e725679e5..f42f1c99e01f072461abaab57d85ad240c6c48ea 100644 (file)
--- a/xmldoc/formats/options/stmsdf-index.xml
+++ b/xmldoc/formats/options/stmsdf-index.xml
@@ -12,4 +12,4 @@
 <para>
        This example will convert route number two and three into separate sdf files:
 </para>
-       <para><command> gpsbabel -i gdb -f routes.gdb -r -o stmsdf,index=2 -F route-one.sdf -r -o stmsdf,index=3 -F route-three.sdf </command></para>
+       <para><userinput> gpsbabel -i gdb -f routes.gdb -r -o stmsdf,index=2 -F route-one.sdf -r -o stmsdf,index=3 -F route-three.sdf </userinput></para>

diff --git a/xmldoc/formats/options/stmwpp-index.xml b/xmldoc/formats/options/stmwpp-index.xml
index 00ddb54b6c2008f3fe22f7e3a8683911657724a0..c43659c2f5380ccde536ab1ba2ef8974152f46de 100644 (file)
--- a/xmldoc/formats/options/stmwpp-index.xml
+++ b/xmldoc/formats/options/stmwpp-index.xml
@@ -5,5 +5,5 @@ tracks read from a more expressive format.  If you have, say, a
 <link linkend="fmt_gpx">gpx</link> file that contains three routes, you may
 use this option to write them one at a time to individual files.
 </para>
-<para><command>gpsbabel -i gpx -f routes.gpx -o stmwpp,index=1 -F route1.txt -o stmwpp,index=2 -F route2.txt -o stmwpp,index=3 -F route3.txt</command></para>
+<para><userinput>gpsbabel -i gpx -f routes.gpx -o stmwpp,index=1 -F route1.txt -o stmwpp,index=2 -F route2.txt -o stmwpp,index=3 -F route3.txt</userinput></para>
 

diff --git a/xmldoc/formats/options/tiger-genurl.xml b/xmldoc/formats/options/tiger-genurl.xml
index 093598a886d0414944f0c657340121fe96717af0..03ebc6d99d09420af8e9794d6b066ce32c4c0768 100644 (file)
--- a/xmldoc/formats/options/tiger-genurl.xml
+++ b/xmldoc/formats/options/tiger-genurl.xml
@@ -6,7 +6,7 @@ a map that will hold all the points to be displayed  and is suitably scaled
 and centered.   
 </para>
 <para>For example:</para>
-<para><command>gpsbabel -i geo -f geocaching.loc -o tiger,genurl=tiger.ctr -F tiger.dat</command></para>
+<para><userinput>gpsbabel -i geo -f geocaching.loc -o tiger,genurl=tiger.ctr -F tiger.dat</userinput></para>
 <para>
 may create tiger.ctr with
 <screen format="linespecific">

diff --git a/xmldoc/formats/palmdoc.xml b/xmldoc/formats/palmdoc.xml
index a20dc06172b69ee1d12a9aa762ab6e00eda6ad12..2ed7ff68b9779e0fe10c4a9ebb695e9074158bf7 100644 (file)
--- a/xmldoc/formats/palmdoc.xml
+++ b/xmldoc/formats/palmdoc.xml
@@ -9,5 +9,5 @@ to a particular waypoint.
 The following command line reads a GPX file with Groundspeak extensions 
 and writes a Palm document with encrypted hints and logs:
 </para>
-<para><command>gpsbabel -i gpx -f 12345.gpx -o "palmdoc,dbname=Unfound Geocaches,encrypt,logs" -F 12345.pdb</command></para>
+<para><userinput>gpsbabel -i gpx -f 12345.gpx -o "palmdoc,dbname=Unfound Geocaches,encrypt,logs" -F 12345.pdb</userinput></para>
     

diff --git a/xmldoc/formats/psp.xml b/xmldoc/formats/psp.xml
index b6949d553a9e7b82a48ba8c3ac596a2782fd983d..70838c26b545f81a0080b6920be125706aca0812 100644 (file)
--- a/xmldoc/formats/psp.xml
+++ b/xmldoc/formats/psp.xml
@@ -55,7 +55,7 @@ There are either no points to write, or you have botched the command
    on the command line.  A simple command line to create PSP files
    looks like this:
 </para>
-<para><command>gpsbabel -i geo -f geocaching.loc -o psp -F NewOrleans.psp</command></para>
+<para><userinput>gpsbabel -i geo -f geocaching.loc -o psp -F NewOrleans.psp</userinput></para>
 <para>
    Note the use of "-f" for INPUT files and "-F" for OUTPUT files.
 </para>

diff --git a/xmldoc/formats/stmsdf.xml b/xmldoc/formats/stmsdf.xml
index 7edbf6ed99d96095b8f05a406c67dbe8318bc48e..9e2f9e01cf092dcc7e386c105370284d6dd41ada 100644 (file)
--- a/xmldoc/formats/stmsdf.xml
+++ b/xmldoc/formats/stmsdf.xml
@@ -15,7 +15,7 @@
                <member>28 = X9 TrackLog</member>
        </simplelist>
 </para>
-       <para><command>gpsbabel -i gpx -f some-routes.gpx -r -o stmsdf,index=3 -F single-route.sdf</command></para>
+       <para><userinput>gpsbabel -i gpx -f some-routes.gpx -r -o stmsdf,index=3 -F single-route.sdf</userinput></para>
 <para>
        <ulink url="http://www.suunto.fi">Suunto Website</ulink>
 </para>

diff --git a/xmldoc/formats/tef.xml b/xmldoc/formats/tef.xml
index c8933e80925c50b16577a81d8386434723607d19..592632d69067919711fefea61a428f21126b4a2a 100644 (file)
--- a/xmldoc/formats/tef.xml
+++ b/xmldoc/formats/tef.xml
@@ -11,5 +11,5 @@ GPSBabel also supports the <link linkend="fmt_bcr">bcr</link> format, which
 may also be used with this program and supports both reading and writing.
 </para>
 
-<para><command> gpsbabel -r -i tef,routevia -f in.xml -o gpx -F out.gpx</command></para>
+<para><userinput> gpsbabel -r -i tef,routevia -f in.xml -o gpx -F out.gpx</userinput></para>
     

diff --git a/xmldoc/formats/text.xml b/xmldoc/formats/text.xml
index 5f8be3037d30838e60c264bf28ea95d22daa3446..28431160bf90cf4dc7657c32881f70a14d10a8ff 100644 (file)
--- a/xmldoc/formats/text.xml
+++ b/xmldoc/formats/text.xml
@@ -4,5 +4,5 @@ handy for listings of any type of waypoint files.
       <para> The following command line reads a GPX file with
 Groundspeak extensions and writes a text file with encrypted hints:
 </para>
-<para><command>gpsbabel -i gpx -f 12345.gpx -o text,encrypt -F 12345.txt</command></para>
+<para><userinput>gpsbabel -i gpx -f 12345.gpx -o text,encrypt -F 12345.txt</userinput></para>
     

diff --git a/xmldoc/formats/wbt-bin.xml b/xmldoc/formats/wbt-bin.xml
index 7d57670ad14eb823d7fbd59c4f1d069a57556f20..94509a517e5cd2e64b5373e44e881daec8d0f1fd 100644 (file)
--- a/xmldoc/formats/wbt-bin.xml
+++ b/xmldoc/formats/wbt-bin.xml
@@ -6,7 +6,7 @@ by Wintec's Windows application.</para>
 </para>
 <example id="wbt-bin-on-macos">
   <title>Command showing conversion of a Wintec binary file to GPX</title>
-  <para><command>gpsbabel -i wbt-bin -f tracks.bin -o
-gpx -F out.gpx</command></para>
+  <para><userinput>gpsbabel -i wbt-bin -f tracks.bin -o
+gpx -F out.gpx</userinput></para>
 </example>
 

diff --git a/xmldoc/formats/wbt.xml b/xmldoc/formats/wbt.xml
index 834d59af15c3c0222a0e1e3dec883a4d8b556d2d..3664d0dacb6b7f0168e3dd9cf94482b7c79128f7 100644 (file)
--- a/xmldoc/formats/wbt.xml
+++ b/xmldoc/formats/wbt.xml
@@ -4,6 +4,6 @@
 </para>
 <example id="wbt-on-macos">
   <title>Command showing WBT-200 download and erase over Bluetooth on Mac OS X</title>
-  <para><command>gpsbabel -i wbt,erase -f /dev/cu.WBT200-SPPslave-1 -o gpx -F out.gpx</command></para>
+  <para><userinput>gpsbabel -i wbt,erase -f /dev/cu.WBT200-SPPslave-1 -o gpx -F out.gpx</userinput></para>
 </example>
     

diff --git a/xmldoc/formats/xmapwpt.xml b/xmldoc/formats/xmapwpt.xml
index aea6eb87d72a2712c41ae45ab13fb4d4cb362d83..3fcb674c7b0fad9c40cc402e0898d594a38e683a 100644 (file)
--- a/xmldoc/formats/xmapwpt.xml
+++ b/xmldoc/formats/xmapwpt.xml
@@ -31,15 +31,15 @@ It should also be noted that <emphasis>reading</emphasis> multiple files
 is indeed possible, but if you have more than a few points, it can be a task. 
 For example:
 </para>
-<para><command>gpsbabel -i xmapwpt -f Xmap1.wpt -f Xmap2.wpt -o mapsend -F mapsend.wpt</command></para>
+<para><userinput>gpsbabel -i xmapwpt -f Xmap1.wpt -f Xmap2.wpt -o mapsend -F mapsend.wpt</userinput></para>
 <para>
 will read the two Xmap .wpt files and write one mapsend file.  This
 is fine for a small handful of points, but could be quite cumbersome
 for folks like me who have 100+ waypoints loaded into XMap.  For *nix
 folks, something as simple as:
 </para>
-<para><command>cat *.wpt > /tmp/foo.wpt</command>
-<command>gpsbabel -i xmapwpt -f foo.wpt -o mapsend -F mapsend.wpt </command></para>
+<para><userinput>cat *.wpt > /tmp/foo.wpt</userinput>
+<userinput>gpsbabel -i xmapwpt -f foo.wpt -o mapsend -F mapsend.wpt </userinput></para>
 <para>
 will do the trick just fine.  
 </para>

diff --git a/xmldoc/gpsbabel_man.xml b/xmldoc/gpsbabel_man.xml
index e0842df8057328ea39b96246fb6abaeb8aa47d05..5545e3609ece0a28d3e7bcf2bdc4b70d0db687b6 100644 (file)
--- a/xmldoc/gpsbabel_man.xml
+++ b/xmldoc/gpsbabel_man.xml
@@ -16,7 +16,7 @@
 
 <refsynopsisdiv>
 <cmdsynopsis>
-<command>gpsbabel</command>
+<userinput>gpsbabel</userinput>
 <arg choice="opt">
   <option>iofFxsh</option>
 </arg>

diff --git a/xmldoc/old/readme.xml b/xmldoc/old/readme.xml
index 807f194ef3c42749b237159e5b2ccec03afd7dd6..fd26feac0c7ba7ea5b5a706a2b61beb91bc4a33d 100644 (file)
--- a/xmldoc/old/readme.xml
+++ b/xmldoc/old/readme.xml
@@ -324,7 +324,7 @@ create a three dimensional IGC file. </para>
 Routenplaner 2002-..." by Map&amp;Guide. It is a route-onle
 format. If you own a newer release (2005...) you can also use the XML
 export and convert via <command moreinfo="none">gpsbabel ... -i tef
-...</command> to your preferred format.  May be there are other
+...</userinput> to your preferred format.  May be there are other
 products from Map&amp;Guide using the format.
 </para>
       <para> Coordinates are stored in Mercator format. The
@@ -1301,7 +1301,7 @@ format.  Intended to serve as source for number-processing
 applications like OpenOffice, Ploticus and others. Tab was chosen as
 delimiter because it is a) supported by both OpenOffice and Ploticus
 and b) is not ',', so you can use <command moreinfo="none">sed -i
-"s/./,/g" &lt;x&gt;.csv'</command> to adapt it to locales where ',' is
+"s/./,/g" &lt;x&gt;.csv'</userinput> to adapt it to locales where ',' is
 used as decimal seperator.  Contributed by Tobias Minich.</para>
     </section>
     <section id="ozi">
@@ -1709,7 +1709,7 @@ handle at least a few thousand of the billion CSV variants available.
 By itself, it doesn't comply to any format, however *most* CSV
 variants can be described as a "style" and fine-tuned by the end user.
 For more information on it's use, please see README.style in the
-style/ sub-directory of <command moreinfo="none">GPSBabel</command>.
+style/ sub-directory of <command moreinfo="none">GPSBabel</userinput>.
 For an example of using the XCSV module within your C program, look at
 the <filename moreinfo="none">ozi.c</filename>, <filename
 moreinfo="none">mxf.c</filename>, and <filename